v1.4.0

Compare Source

=========================

Features

• #&#8203;463 <https://github.com/pytest-dev/pluggy/issues/463>_: A warning :class:~pluggy.PluggyTeardownRaisedWarning is now issued when an old-style hookwrapper raises an exception during teardown.
  See the warning documentation for more details.

• #&#8203;471 <https://github.com/pytest-dev/pluggy/issues/471>_: Add :func:PluginManager.unblock <pluggy.PluginManager.unblock> method to unblock a plugin by plugin name.

Bug Fixes

• #&#8203;441 <https://github.com/pytest-dev/pluggy/issues/441>_: Fix :func:~pluggy.HookCaller.call_extra() extra methods getting ordered before everything else in some circumstances. Regressed in pluggy 1.1.0.

• #&#8203;438 <https://github.com/pytest-dev/pluggy/issues/438>_: Fix plugins registering other plugins in a hook when the other plugins implement the same hook itself. Regressed in pluggy 1.1.0.

v1.3.0

Compare Source

=========================

Deprecations and Removals

• #&#8203;426 <https://github.com/pytest-dev/pluggy/issues/426>_: Python 3.7 is no longer supported.

Features

• #&#8203;428 <https://github.com/pytest-dev/pluggy/issues/428>_: Pluggy now exposes its typings to static type checkers.

  As part of this, the following changes are made:

  • Renamed _Result to Result, and exported as :class:pluggy.Result.
  • Renamed _HookRelay to HookRelay, and exported as :class:pluggy.HookRelay.
  • Renamed _HookCaller to HookCaller, and exported as :class:pluggy.HookCaller.
  • Exported HookImpl as :class:pluggy.HookImpl.
  • Renamed _HookImplOpts to HookimplOpts, and exported as :class:pluggy.HookimplOpts.
  • Renamed _HookSpecOpts to HookspecOpts, and exported as :class:pluggy.HookspecOpts.
  • Some fields and classes are marked Final and @final.
  • The :ref:api-reference is updated to clearly delineate pluggy's public API.

  Compatibility aliases are put in place for the renamed types.
  We do not plan to remove the aliases, but we strongly recommend to only import from pluggy.* to ensure future compatibility.

  Please note that pluggy is currently unable to provide strong typing for hook calls, e.g. pm.hook.my_hook(...),
  nor to statically check that a hook implementation matches the hook specification's type.

v1.2.0

Compare Source

=========================

Features

• #&#8203;405 <https://github.com/pytest-dev/pluggy/issues/405>_: The new-style hook wrappers, added in the yanked 1.1.0 release, now require an explicit wrapper=True designation in the @hookimpl() decorator.

v1.1.0

Compare Source

=====================

.. note::

This release was yanked because unfortunately the implicit new-style hook wrappers broke some downstream projects.
See #&#8203;403 <https://github.com/pytest-dev/pluggy/issues/403>__ for more information.
This was rectified in the 1.2.0 release.

Deprecations and Removals

• #&#8203;364 <https://github.com/pytest-dev/pluggy/issues/364>_: Python 3.6 is no longer supported.

Features

• #&#8203;260 <https://github.com/pytest-dev/pluggy/issues/260>_: Added "new-style" hook wrappers, a simpler but equally powerful alternative to the existing hookwrapper=True wrappers.

  New-style wrappers are generator functions, similarly to hookwrapper, but do away with the :class:result <pluggy.Result> object.
  Instead, the return value is sent directly to the yield statement, or, if inner calls raised an exception, it is raised from the yield.
  The wrapper is expected to return a value or raise an exception, which will become the result of the hook call.

  New-style wrappers are fully interoperable with old-style wrappers.
  We encourage users to use the new style, however we do not intend to deprecate the old style any time soon.

  See :ref:hookwrappers for the full documentation.

• #&#8203;364 <https://github.com/pytest-dev/pluggy/issues/364>_: Python 3.11 and 3.12 are now officially supported.

• #&#8203;394 <https://github.com/pytest-dev/pluggy/issues/394>_: Added the :meth:~pluggy.Result.force_exception method to _Result.

  force_exception allows (old-style) hookwrappers to force an exception or override/adjust an existing exception of a hook invocation,
  in a properly behaving manner. Using force_exception is preferred over raising an exception from the hookwrapper,
  because raising an exception causes other hookwrappers to be skipped.